Systems and methods for backflow management

ABSTRACT

Systems, methods, and articles of manufacture for automatic backflow identification, detection, remediation, and/or management. In some embodiments, a backflow management device may comprise a threaded and electronically-enabled plug installed in a non-pressurized pipe system cleanout, branch, or stub.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims benefit and priority under 35 U.S.C. § 120 to,and is a Continuation of, International Patent Application No.PCT/US22/14457 filed on Jan. 29, 2022 and titled “SYSTEMS AND METHODSFOR BACKFLOW MANAGEMENT” and which itself claims benefit and priorityunder 35 U.S.C. § 119(e) to, and is a Non-provisional of, U.S.Provisional Patent Application No. 63/143,153 filed on Jan. 29, 2021 andtitled “SYSTEMS AND METHODS FOR SEWAGE BLOCKAGE MANAGEMENT”, which ishereby incorporated by reference herein in its entirety.

BACKGROUND

Pressurized fluid conduits are often equipped with backflow preventiondevices (e.g., one-way valves) to permit fluid flow in a first directionwhile preventing flow in the reverse/second direction. Such devices arenot installed in non-pressurized (e.g., open channel) conduits as theunpressurized flow is typically not capable of forcing the one-way valveopen to permit flow in the first direction. Non-pressurized fluid flowsystems are often equipped with reservoirs or holding tanks in whichfloat valves may be placed to regulate the downstream non-pressurizedflow. Should a backup occur in such non-pressurized fluid flow systemsit may often only be detected by observation of undesirable upstreamresults such as backflow flooding. In the case that the non-pressurizedfluid flow system comprises a sewage or sanitary disposal system, suchbackflow occurrences can be both costly and time consuming to remediate.

BRIEF DESCRIPTION OF THE DRAWINGS

An understanding of embodiments described herein and many of theattendant advantages thereof may be readily obtained by reference to thefollowing detailed description when considered with the accompanyingdrawings, wherein:

FIG. 1 is a block diagram of a system according to some embodiments;

FIG. 2 is a block diagram of a system according to some embodiments;

FIG. 3A, FIG. 3B, FIG. 3C, FIG. 3D, FIG. 3E, FIG. 3F, FIG. 3G, FIG. 3H,and FIG. 3I are various views of a backflow management device accordingto some embodiments;

FIG. 4 is a perspective diagram of a system according to someembodiments;

FIG. 5 is a flow diagram of a method according to some embodiments; and

FIG. 6 is a block diagram of an apparatus according to some embodiments.

DETAILED DESCRIPTION

I. Introduction

Embodiments presented herein are descriptive of systems, apparatus,methods, and articles of manufacture for backflow management. In someembodiments, a backflow management device may be installed in anon-pressurized fluid flow cleanout, for example, and may utilize one ormore electronic sensors to monitor the fluid level in the cleanout. Insome embodiments, the backflow management device may wirelesslycommunicate backflow detection events to a networked processing devicesuch as a central controller and/or a user's mobile electronic device.In some embodiments, the networked processing device may be triggered bythe event to send an alert, schedule a service appointment, and/orautomatically activate a fluid inflow device (e.g., to preventadditional non-pressurized flow from being generated). According to someembodiments, the backflow management device may comprise a housingshaped to replicate and/or replace a four-inch (4″) or six-inch (6″)diameter Drain, Waste, and Vent (DWC) PolyVinyl Chloride (PVC) cleanoutplug Charlotte Pipe and Foundry Company of Charlotte, NC. In such amanner, for example, the backflow management device may be threaded intoan existing cleanout in replace of a standard plug and may automaticallymeasure, monitor, and trigger backflow event actions utilizing wirelesscommunications.

Typical non-pressurized/open-channel fluid flow systems such as sewer,sanitary, and drainage systems do not comprise in-conduit measurementdevices. Accordingly, such systems are prone to undetected backup eventsthat can cause significant damage to associated buildings andstructures. Sewage or drainage backflows can cause flooding inside ofstructures including inhabited spaces, for example, which may result innecessary evacuation, extensive cleaning/decontamination, andreplacement of building materials and/or furnishings.

Embodiments for backflow management systems, methods, and devicespresented herein solve these and other deficiencies of non-pressurizedfluid flow systems, reducing the likelihood of damage and remedialexpense.

II. Backflow Management Systems and Devices

Turning initially to FIG. 1 , a block diagram of a system 100 accordingto some embodiments is shown. In some embodiments, the system 100 maycomprise one or more user devices 102 a-b communicatively coupled to anetwork 104. In some embodiments, the user devices 102 a-b and/or thenetwork 104 may also or alternatively be coupled to a third-party device106 and/or may be disposed in and/or associated with a building 108(e.g., a first user device 102 a may be disposed in the building 108while a second user device 102 b may be disposed outside of and/orremote form the building 108). The building 108 (and/or other type ofstructure) may comprise and/or define, in some embodiments, a fluidinlet 108-1 and/or a fluid outlet 108-2. The fluid inlet 108-1 maycomprise, for example, a water service line, well line, gas inlet,and/or one or more other point and/or non-point sources of fluid.According to some embodiments, the fluid outlet 108-2 may comprise oneor more drains and/or other effluent conduits such as a sanitary drain,storm drain, greywater drain, and/or vent. In some embodiments, the userdevices 102 a-b and/or the third-party device 106 may be incommunication with (e.g., via the network 104) one or more of acontroller device 110, an inlet device 130, a memory device 140, and/oran outlet device 150 (e.g., a backflow detection and/or managementdevice). According to some embodiments, the outlet device 150 maycomprise a sensor such as a pressure transducer, an imaging device, aLight Detection And Ranging (LiDAR) device, and/or an acoustic sensor,that is disposed to capture data descriptive of the outlet 108-2 (e.g.,a fluid level and/or presence thereof).

In accordance with some embodiments herein, the user devices 102 a-b maybe utilized to direct, manage, and/or interface with the outlet device150 to capture pressure readings (and/or other sensor data) of theoutlet 108-2 (e.g., within an outlet and/or effluent conduit defined bythe outlet 108-2). In some embodiments, the captured readings/data maybe provided from the outlet device 150 to one or more of the userdevices 102 a-b (and/or the controller device 110) for readings/sensordata analysis and execution of stored analysis rules and/or logic. Insuch a manner, for example, data descriptive of the outlet 108-2 may beinput into the system 100 and utilized to detect, respond to, and/orotherwise manage backflow events.

Fewer or more components 102 a-b, 104, 106, 108, 108-1, 108-2, 110, 130,140, 150 and/or various configurations of the depicted components 102a-b, 104, 106, 108, 108-1, 108-2, 110, 130, 140, 150 may be included inthe system 100 without deviating from the scope of embodiments describedherein. In some embodiments, the components 102 a-b, 104, 106, 108,108-1, 108-2, 110, 130, 140, 150 may be similar in configuration and/orfunctionality to similarly named and/or numbered components as describedherein. In some embodiments, the system 100 (and/or portions thereof)may comprise an automatic backflow detection and/or management program,system, and/or platform programmed and/or otherwise configured toexecute, conduct, and/or facilitate the method 500 of FIG. 5 herein,and/or portions thereof.

The user devices 102 a-b, in some embodiments, may comprise any type orconfiguration of computing, mobile electronic, network, user, and/orcommunication devices that are or becomes known or practicable. The userdevices 102 a-b may, for example, comprise one or more tablet computers,such as an iPad® manufactured by Apple®, Inc. of Cupertino, CA, and/orcellular and/or wireless telephones or “smart” phones, such as aniPhone® (also manufactured by Apple®, Inc.) or an Optimus™ S smart phonemanufactured by LG® Electronics, Inc. of San Diego, CA, and running theAndroid® operating system from Google®, Inc. of Mountain View, CA. Insome embodiments, the user devices 102 a-b may comprise one or moredevices owned and/or operated by one or more users, such as a buildingmanager/superintendent, contractor, plumber, home owner, insuranceinspector, building inspector, etc. According to some embodiments, theuser devices 102 a-b may communicate with the controller device 110 viathe network 104 to provide and/or relay readings and/or other datacaptured and/or recorded by the outlet device 150 for backflowdetection, mitigation, response, cleanup, and/or management, asdescribed herein. According to some embodiments, the user devices 102a-b may store and/or execute specially programmed instructions (such asa mobile device application) to operate in accordance with embodimentsdescribed herein. The user devices 102 a-b may, for example, execute oneor more mobile device programs that activate and/or control the outletdevice 150 and/or that analyze readings and/or other data of the outlet108-2, e.g., to identify potential backflow events and/or conditions,automatically contact and/or schedule service and/or emergency responseservices, and/or automatically conduct mitigation efforts such as (butnot limited to) closing (and/or otherwise adjusting a setting of) theinlet device 130.

The network 104 may, according to some embodiments, comprise a LocalArea Network (LAN; wireless and/or wired), cellular telephone,Bluetooth® and/or Bluetooth Low Energy (BLE), Near Field Communication(NFC), and/or Radio Frequency (RF) network with communication linksbetween the controller device 110, the user devices 102 a-b, thethird-party device(s) 106, the inlet device 130, the outlet device 150,and/or the memory device 140. In some embodiments, the network 104 maycomprise direct communications links between any or all of thecomponents 102 a-b, 106, 110, 130, 140, 150 of the system 100. The userdevices 102 a-b may, for example, be directly interfaced or connected toone or more of the outlet device 150 and/or the controller device 110via one or more wires, cables, wireless links, and/or other networkcomponents, such network components (e.g., communication links)comprising portions of the network 104. In some embodiments, the network104 may comprise one or many other links or network components otherthan those depicted in FIG. 1 . The outlet device 150 and/or the userdevices 102 a-b may, for example, be connected to the controller device110 via various cell towers, routers, repeaters, ports, switches, and/orother network components that comprise the Internet and/or a cellulartelephone (and/or Public Switched Telephone Network (PSTN)) network, andwhich comprise portions of the network 104.

While the network 104 is depicted in FIG. 1 as a single object, thenetwork 104 may comprise any number, type, and/or configuration ofnetworks that is or becomes known or practicable. According to someembodiments, the network 104 may comprise a conglomeration of differentsub-networks and/or network components interconnected, directly orindirectly, by the components 102 a-b, 106, 110, 130, 140, 150 of thesystem 100. The network 104 may comprise one or more cellular telephonenetworks with communication links between the user devices 102 a-b, theoutlet device 150, and the controller device 110, for example, and/ormay comprise a BLE, NFC, RF, and/or “personal” network comprisingshort-range wireless communications between a first user device 102 a(e.g., disposed in or proximate to the building 108) and the outletdevice 150, for example.

The third-party device 106, in some embodiments, may comprise any typeor configuration of a computerized processing device, such as a PC,laptop computer, computer server, database system, and/or otherelectronic device, devices, or any combination thereof. In someembodiments, the third-party device 106 may be owned and/or operated bya third-party (i.e., an entity different than any entity owning and/oroperating any of the user devices 102 a-b, the building 108, the outletdevice 150, and/or the controller device 110). The third-party device106 may, for example, be owned and/or operated by a data and/or dataservice provider, such as Dun & Bradstreet® Credibility Corporation(and/or a subsidiary thereof, such as Hoovers™), Deloitte® Development,LLC, Experian™ Information Solutions, Inc., and/or Edmunds.com®, Inc. Insome embodiments, the third-party device 106 may supply and/or providedata, such as location data, encryption/decryption data, configurationdata, and/or preference data to the controller device 110, the userdevices 102 a-b, and/or the outlet device 150. In some embodiments, thethird-party device 106 may comprise a plurality of devices and/or may beassociated with a plurality of third-party entities. According to someembodiments, the third-party device 106 may comprise the memory 140 (ora portion thereof), such as in the case the third-party device 106comprises a third-party data storage service, device, and/or system,such as the Amazon® Simple Storage Service (Amazon® S3™) available fromAmazon.com, Inc. of Seattle, WA or an open-source third-party databaseservice, such as MongoDB™ available from MongoDB, Inc. of New York, NY.In some embodiments, the third-party device 106 may comprise aproprietary communication server operable to communicate with and/orcontrol the inlet device 130.

According to some embodiments, the building 108 may comprise anylocation, object, and/or structure desired for analysis and/ormonitoring, such as a location of an insured object, a location of acustomer, a location of an account and/or business, etc. In someembodiments, the building 108 may be identified by one or more locationparameters, such as an address, postal code, map quadrant, and/or one ormore coordinates and/or other identifiers (e.g., a unique geo-referencedlocation identifier). According to some embodiments, the building 108may comprise and/or define a fluid system in which fluid is provided toand enters the building 108 via the inlet 108-1 (e.g., and may becontrolled, monitored, and/or measured by the inlet device 130), isutilized for some purpose within the building 108 (e.g., potable water,process supply water, natural gas, propane gas, conditioned air,purification and/or cleaning, etc.), and some portion thereof exits thebuilding 108 via the outlet 108-2. The building 108 may comprise abalanced system wherein substantially all fluid entering the buildingvia the inlet 108-1 exits the building via the outlet 108-2 or maycomprise an unbalanced system that includes additional fluid sourceand/or effluents (not shown). According to some embodiments, the inlet108-1 may comprise a water supply to the building 108 and the outlet108-2 may comprise a sewer or sanitary drain line exiting the building(e.g., and connecting to a sewer main or septic system, neither of whichare separately shown).

In some embodiments, the controller device 110 may comprise anelectronic and/or computerized controller device, such as a computerserver and/or server cluster communicatively coupled to interface withthe user devices 102 a-b and/or the outlet device 150 (directly and/orindirectly). The controller device 110 may, for example, comprise one ormore PowerEdge™ M910 blade servers manufactured by Dell®, Inc. of RoundRock, TX, which may include one or more Eight-Core Intel® Xeon® 7500Series electronic processing devices. According to some embodiments, thecontroller device 110 may be located remotely from one or more of theuser devices 102 a-b and/or the outlet device 150. The controller device110 may also or alternatively comprise a plurality of electronicprocessing devices located at one or more various sites and/or locations(e.g., a distributed computing and/or processing network) inside and/oroutside of the building 108.

According to some embodiments, the controller device 110 may storeand/or execute specially-programmed instructions to operate inaccordance with embodiments described herein. The controller device 110may, for example, execute one or more programs that facilitate and/orcause the automatic detection, verification, data capture, and/or dataanalysis of the outlet 108-2 (e.g., via the outlet device 150), asdescribed herein. According to some embodiments, the controller device110 may comprise a computerized processing device, such as a PC, laptopcomputer, computer server, and/or other network or electronic device,operated to manage and/or facilitate backflow analysis in accordancewith embodiments described herein.

In some embodiments, the inlet device 130 may comprise any type and/orconfiguration of mechanical, electric, and/or electro-mechanical devicethat is operable to provide data descriptive of the inlet 108-1 (and/orfluid thereof; not shown). The inlet device 130 may comprise, forexample, a meter (and/or a valve) such as a Neptune™ T-10® ¾″ PotableWater Meter available from Neptune Technology Group Inc. of Tallassee,AL or a StreamLabs® Smart Home Water Monitor available from Fresh WaterSystems of Greenville, NC. According to some embodiments, the inletdevice 130 may comprise an actuator and/or automatic valve such as aBelimo® CMB24-L-100D volumetric flow controller and/or a Belimo®EXT-B2050-PWV-NPT+CQBUP-3 2-way potable water valve, both available fromBelimo Aircontrols (USA), Inc. of Danbury, CT. In some embodiments, theinlet device 130 may be controllable via the network 104 and/or byand/or via the user devices 102 a-b and/or the third-party device 106.

In some embodiments, the controller device 110, the user devices 102a-b, and/or the outlet device 150 may be in communication with thememory device 140. The memory device 140 may store, for example, mobiledevice application data, fluid measurement data, user data, damageestimation data, location data (such as coordinates, distances, etc.),security access protocol and/or verification data, service providercontact data, scoring data, qualitative assessment data and/or logic,and/or instructions that cause various devices (e.g., the controllerdevice 110, the user devices 102 a-b, and/or the outlet device 150) tooperate in accordance with embodiments described herein. In someembodiments, the memory device 140 may comprise any type, configuration,and/or quantity of data storage devices that are or become known orpracticable. The memory device 140 may, for example, comprise an arrayof optical and/or solid-state hard drives configured to storefluid/backflow data, device identifier data, location data, ArtificialIntelligence (AI) module(s), image analysis data, and/or damageestimation data provided by (and/or requested by) the user devices 102a-b and/or the third-party device 106, and/or various operatinginstructions, drivers, etc. In some embodiments, the memory device 140may comprise a stand-alone and/or networked data storage device, such asa solid-state and/or non-volatile memory card (e.g., a Secure Digital(SD) card, such as an SD Standard-Capacity (SDSC), an SD High-Capacity(SDHC), and/or an SD eXtended-Capacity (SDXC), and any variouspracticable form-factors, such as original, mini, and micro sizes, suchas those available from Western Digital Corporation of San Jose, CA).While the memory device 140 is depicted as a stand-alone component ofthe system 100 in FIG. 1 , the memory device 140 may comprise multiplecomponents. In some embodiments, a multi-component memory device 140 maybe distributed across various devices and/or may comprise remotelydispersed components. Any or all of the user devices 102 a-b, thethird-party device 106, the controller device 110, the inlet device 130,and/or the outlet device 150 may comprise the memory device 140 or aportion thereof, for example.

The outlet device 150, in some embodiments, may comprise any type orconfiguration of sensor, device, and/or object that is capable ofcapturing fluid readings and/or other data descriptive of the building108 and/or the outlet 108-2 thereof. The outlet device 150 may comprise,for example, one or more pressure transducers such as a ProSense™ MPS25series mechanical pressure switch, a ProSense™ PSD25 series electronicpressure switch, and/or a ProSense™ EPS Series Digital Pressure Sensor,all available from AutomationDirect.com of Cumming, GA, or a PFT510Miniature Pressure Sensor (Miniature Flush Mount Diaphragm) availablefrom FUTEK® Advanced Sensor Technology, Inc. of Irvine, CA. The outletdevice 150 may, in some embodiments, utilize any fluid sensingtechnology and/or methodology that is or becomes known or practicablesuch as, but not limited to, diaphragm displacement, strain gauge-basedtransduction, LiDAR, acoustic, microwave, Infrared Radiation (IR),capacitance, potentiometric, and/or resonance.

Referring now to FIG. 2 , a block diagram of a system 200 according tosome embodiments is shown. The system 200 may comprise, for example, afluid conduit 208-2 in which a fluid 208-3 is disposed. In someembodiments, such as depicted din FIG. 2 for purposes of non-limitingexample, the fluid conduit 208-2 may comprise a riser, end-run, and/orcleanout in fluid communication with an outlet and/or effluent path (notseparately shown) such as a sewage or sanitary cleanout of a building(not shown; e.g., the building 108 of FIG. 1 ). According to someembodiments, the fluid conduit 208-2 may comprise a four-inch (4″) orsix-inch (6″) PVC pipe cleanout and/or cleanout adapter sectionconfigured to be selectively sealed and opened with a standard threadedplug (not shown). In some embodiments, the fluid conduit 208-2 mayinstead be selectively sealed or opened by installation (or removal) ofa threaded backflow management device 250.

In some embodiments, the backflow management device 250 may bestructurally similar to a standard plug (e.g., circular or cylindricalin shape with threads configured to mate with corresponding threads ofthe fluid conduit 208-2) but may specially outfitted and/or programmedto detect backflow events and in response to such detections, executeand/or initiate backflow management processes as described herein. Thebackflow management device 250 may comprise, for example, an electronicprocessing device 212 coupled to a wireless communication device 214. Insome embodiments, the backflow management device 250 may comprise aplurality of input devices 216 a-c such as a power input 216 a (e.g., afirst input, such as a power connection port), a sensor 216 b (e.g., apressure and/or other fluid sensor), and/or a user input device 216 c(e.g., a button, switch, etc.). According to some embodiments, thebackflow management device 250 may comprise an output device 218 such asa light and/or sounder device to provide user feedback and/or statusindications. In some embodiments, the power input 216 a may be connectedto an internal power supply 232 (such as a battery and/or capacitor)that provides power to any or all of the processing device 212, thewireless communication device 214, the sensor 216 b, and/or the outputdevice 218.

According to some embodiments, some or all of the electrical components212, 214, 216 a-c, 218, 232, may be housed within a housing 252 definedby the backflow management device 250. The backflow management device250 and/or housing 252 thereof may, for example, comprise and/or definean interior volume 252-2 in which the electrical components 212, 214,216 a-c, 218, 232 are disposed. In some embodiments, the housing 252(and/or the backflow management device 250) may be selectively sealed,opened, and/or closed by installation or removal of a cover 260 that isconfigured to mate with the housing 252 to seal the interior volume252-2. In some embodiments, a seal and/or gasket (not shown) may beutilized at the interface between the housing 252 and the cover 260 toprevent (or minimize) the fluid 208-3 from entering the interior volume252-2.

In some embodiments, the backflow management device 250 and/or the cover260 thereof may comprise and/or define an exterior projection or port262 via which the sensor 216 b may be exposed to, in communication with,and/or interfaced with the fluid 208-3 (and/or an interior of the fluidconduit 208-2). The sensor 216 b may, for example, acquire readingsdescriptive of the fluid 208-3 such as a distance to a surface of thefluid 208-3, a pressure exerted by the fluid 208-3 (directly orindirectly), a temperature of the fluid 208-3, etc. The backflowmanagement device 250 may, in some embodiments, be programmed toreceive, store, and/or analyze these readings to identify a potentialbackflow event. The backflow management device 250 may be programmedand/or set/configured for different physical installation situations. Inthe case that the fluid conduit 208-2 comprises a vertical risercleanout of a sewage or sanitary drain, for example, detection of thefluid 208-3 alone may be indicative of a backflow event and the backflowmanagement device 250 may be programmed to indicate and alert conditionand/or backflow event occurrence in response thereto (e.g., bygenerating output via the output device 218 and/or by transmitting oneor more signals via the wireless communication device 214). In the casethat the fluid conduit 208-2 comprises a horizontal or Y-junctioncleanout (e.g., oriented differently than depicted in FIG. 2), thepresence of the fluid 208-3 may not be indicative of a backflow event,but certain qualities of the fluid 208-3 such as depth, distance (e.g.,from the sensor 216 b), temperature, flow rate, etc., may be indicativeof a backflow event and rules for identifying such events may beprogrammed into the backflow management device 250 to cause outputand/or alerts. In some embodiments, a cap 270 may retain a filter,diaphragm, and/or screen 272 covering the port 262, e.g., to preventfouling and/or damage to the sensor 216 b from the fluid 208-3, and/orto provide a mechanism for easy cleaning and/or maintenance thereof.

Fewer or more components 208-2, 208-3, 212, 214, 216 a-c, 218, 232, 250,252, 252-2, 260, 262, 270, 272 and/or various configurations of thedepicted components 208-2, 208-3, 212, 214, 216 a-c, 218, 232, 250, 252,252-2, 260, 262, 270, 272 may be included in the system 200 withoutdeviating from the scope of embodiments described herein. In someembodiments, the components 208-2, 208-3, 212, 214, 216 a-c, 218, 232,250, 252, 252-2, 260, 262, 270, 272 may be similar in configurationand/or functionality to similarly named and/or numbered components asdescribed herein. In some embodiments, the system 200 (and/or portionsthereof) may comprise an automatic backflow detection and/or managementprogram, system, and/or platform programmed and/or otherwise configuredto execute, conduct, and/or facilitate the method 500 of FIG. 5 herein,and/or portions thereof.

Turning to FIG. 3A, FIG. 3B, FIG. 3C, FIG. 3D, FIG. 3E, FIG. 3F, FIG.3G, FIG. 3H, and FIG. 3I, various views of a backflow management device350 according to some embodiments are shown. The backflow managementdevice 350 may comprise, for example, a plurality of input devices 316a-b and/or output devices 318 a-b (e.g., secured in place and/orprotected via a cover 318-1) coupled to, retained, and/or housed by ahousing 352. In some embodiments, the housing 352 may comprise and/ordefine a top surface 352-1 (that may be circular in shape; FIG. 3A andFIG. 3C) and/or may define an interior volume 352-2 comprising aninterior surface 352-3 (FIG. 3F). According to some embodiments, thehousing 352 may comprise and/or define one or more sides 352-4 (FIG. 3A,FIG. 3B, and FIG. 3E), which in the case that the backflow managementdevice 350 and/or the housing 352 is cylindrically shaped as depicted,may comprise a single continuous side of the cylinder. In someembodiments, the housing 352 may comprise one or more holes or passages354 a-d that are formed and/or cut between the top surface 352-1 and theinterior surface 352-3. As depicted in FIG. 3A, FIG. 3B, and FIG. 3C,the input devices 316 a-b and/or output devices 318 a-b may be coupledand/or installed to be disposed in or through the passages 354 a-d.

According to some embodiments, the backflow management device 350 maycomprise and/or define a projection or nub 356 comprising and/ordefining a top surface 356-1, a chamber 356-2 comprising an interiorsurface 356-3, and/or sides 356-4. As depicted, the top surface 356-1 ofthe nub 356 may be disposed in a plane that is parallel but offset fromthe top surface 352-1 of the housing 352 and/or the interior surface356-3 of the nub 356 may be disposed in a plane that is parallel butoffset from the interior surface 352-3 of the housing 352. In someembodiments, each of the top surface 352-1, the interior surface 352-3,the top surface 356-1, and the interior surface 356-3 may be disposed inparallel but offset planes. In some embodiments, the sides 356-4 of thenub 356 may be utilized to engage and/or disengage threads 358 on theside(s) 352-4 of the housing 352 with corresponding threads (not shown)in a riser or cleanout pipe and/or pipe adapter, such as by providingtorque surfaces that are operable to receive rotational force applied totwo or more of the sides 356-4 and transfer the rotational force to thethreads 358.

In some embodiments, the housing 352 and/or the interior volume 352-2thereof may be selectively sealed by coupling and/or mating of a cover360 thereto. The cover 360 may comprise, for example, an outer surface360-1 and/or may define an interior volume 360-2 comprising an interiorsurface 360-3. According to some embodiments, the cover 360 may compriseand/or define one or more sides 360-4 such as the circular wall or axialflange as depicted in FIG. 3E and FIG. 3G. In some embodiments, the side360-4 may be shaped and/or sized to mate with and/or seat within theinterior volume 352-2 of the housing 352. According to some embodiments,the cover 360 may comprise and/or define a flange 360-5 that, e.g., incooperation with the side 360-4 couples to the housing 352 to seal theinterior volume 352-2.

According to some embodiments, the cover 360 (and/or the backflowmanagement device 350) may comprise and/or define an exterior projection362 comprising a bore 364 that extends through the cover 360. In someembodiments, the cover 360 may comprise and/or define a plurality ofmounts 366 a-e disposed and/or formed on the interior surface 360-3.According to some embodiments, the exterior projection 362 may comprisethreads 368 that are configured to mate with and couple to a cap 370.The cap 370 may, for example, define a seat 370-1 in which a screen 372may be disposed such that in the case that the cap 370 is installed uponthe exterior projection 362 the screen 372 is retained to cover the bore364. In such a manner, for example, the cap 370 may be utilized toselectively install or remove the screen 372 from the bore 364. The cap370 may, in some embodiments, be annular in shape and/or define a hole374 that permits the screen 372 and/or the bore 364 to be incommunication (e.g., fluid communication) with the environment outsideof the backflow management device 350 (e.g., on the side of the cover360).

In some embodiments, a circuit board 380 such as a Printed Circuit Board(PCB) may be coupled and/or retained in the interior volume 352-2 of thehousing 352. As depicted in FIG. 3E, the circuit board 380 may becircular in shape and/or may be sandwiched between the housing 352 andthe cover 360. The circuit board 380 may, for example, be mounted to aplurality of the mounts 366 b-e of the cover 360 utilizing fasteners 390such as the depicted screws. According to some embodiments, a pressuretransducer or other sensor (not shown; e.g., the sensor 216 b of FIG. 2herein) may be aligned with and/or mounted into the bore 364 via a firstmount 366 a (e.g., situated in the center of the interior surface 360-3of the cover 360, as depicted in FIG. 3G). In some embodiments, theinput devices 316 a-b and/or output devices 318 a-b may be coupled tothe circuit board 380 such that they align with respective passages 354a-d in the housing 352. According to some embodiments, a first inputdevice 316 a may comprise a power input, a second input device 316 b maycomprise a button or switch, a first output device 318 a may comprise afirst color light such as a Light Emitting Diode (LED), and/or a secondoutput device 318 b may comprise a second color light/LED. In someembodiments, other electronic devices (not separately shown) may becoupled to and/or disposed or formed on the circuit board 380 and/or maybe in communication with the input devices 316 a-b and/or the outputdevices 318 a-b, e.g., to conduct backflow management processes asdescribed herein.

According to some embodiments, the circuit board 380 may comprise and/orbe coupled to a sensor that itself is aligned with and/or coupled to afirst mount 366 a of the cover 360. The screen 372 may protect, shield,and/or filter the sensor from any fluid (not shown) that passes throughthe hole 374 of the cap 372 and into the bore 364. In such a manner, forexample, the sensor may be disposed to acquire data descriptive of thefluid and/or of an environment adjacent to the outer surface 360-1 ofthe cover 360. The cover 360 may be coupled to the housing 352 toprotect the circuit board 380 (e.g., and the sensor) from any exteriorfluids. In some embodiments, such as the case in which the threads 358of the housing 352 are engaged with and/or coupled and/or mated tocorresponding threads of a fluid conduit (e.g., a non-pressurized and/oropen-channel flow conduit; not shown), the environment sensed and/ormeasured by the sensor may comprise an environment internal to theconduit. According to some embodiments, the backflow management device350 may identify a backflow (and/or other programmed and/or predefined)event based on the sensor readings/data and may provide indications ofthe readings/data and/or identification (e.g., an alert) via one or moreof the output devices 318 a-b (and/or via a wireless communicationdevice coupled to and/or integrated with the circuit board 380; notshown). The backflow management device 350 may cause the first outputdevice (e.g., a green LED) to illuminate in the case that no backflow(and/or other alert) event is detected, for example, and/or may causethe second output device (e.g., a red LED) to illuminate in the casethat a backflow (and/or other alert) event is detected. In someembodiments, the backflow management device 350 may be powered via thefirst input device 316 a (e.g., a Direct Current (DC) power supplyconnector) and/or may comprise one or more power supplies and/or sources(not shown) integrated with the circuit board 380. According to someembodiments, the second input device 318 b may comprise a button thatpermits a user to turn the backflow management device 350 on or off,reset the backflow management device 350, pair the backflow managementdevice 350 with another electronic device (not shown; e.g., via ashort-range wireless communications protocol such as Bluetooth®), and/orswitch the backflow management device 350 amongst and/or betweendifferent modes.

In some embodiments, such as depicted in FIG. 3I, a wrench 392 may beutilized (e.g., coupled and/or mated) to apply rotational forces/torqueto the backflow management device 350. The wrench 392 may, for example,comprise a molded, cast, printed, and/or otherwise formed objectcomprising and/or defining a handle portion 394 that is elongated alongan axis and an opening 396 disposed near one end of the wrench 392.According to some embodiments, the opening 396 may be shaped and/orsized to fit over the nub 356 such that the sides 356-4 of the nub 356engage and/or mate with at least two corresponding sides of the opening396. Although depicted as a square opening 396 and square nub 356,additional or alternate cooperative geometries may be utilized. In someembodiments, the opening 396 and/or the nub 356 may be sized and/orshaped to prevent rotational engagement in at least one direction. Thewrench 392 may only be operable to engage with the backflow managementdevice 350 in a first rotational direction such as to tighten or installthe backflow management device 350, for example, or may only be operableto engage with the backflow management device 350 in a second (e.g.,reverse) rotational direction such as to loosen or uninstall thebackflow management device 350. In such embodiments, a first version ofthe wrench 392 may be provided for tightening/installation and a secondversion (not shown) of the wrench 392 may be provided forloosening/uninstallation.

While various sizes, quantities, dimensions, and/or proportions ofvarious elements and/or features of the backflow management device 350are described and/or depicted, in some embodiments, different sizes,quantities, dimensions, and/or proportions of the various elements maybe utilized. Similarly, mating and/or other cooperative and/orcorresponding elements may be reversed in some embodiments.

Fewer or more components 316 a-b, 318 a-b, 318-1, 352, 352-1, 352-2,352-3, 352-4, 354 a-d, 356, 356-1, 356-2, 356-3, 356-4, 358, 360, 360-1,360-2, 360-3, 360-4, 360-5, 362, 364, 366 a-e, 368, 370, 370-2, 372,374, 380, 390, 392, 394, 396 and/or various configurations of thedepicted components 316 a-b, 318 a-b, 318-1, 352, 352-1, 352-2, 352-3,352-4, 354 a-d, 356, 356-1, 356-2, 356-3, 356-4, 358, 360, 360-1, 360-2,360-3, 360-4, 360-5, 362, 364, 366 a-e, 368, 370, 370-2, 372, 374, 380,390, 392, 394, 396 may be included in the backflow management device 350without deviating from the scope of embodiments described herein. Insome embodiments, the components 316 a-b, 318 a-b, 318-1, 352, 352-1,352-2, 352-3, 352-4, 354 a-d, 356, 356-1, 356-2, 356-3, 356-4, 358, 360,360-1, 360-2, 360-3, 360-4, 360-5, 362, 364, 366 a-e, 368, 370, 370-2,372, 374, 380, 390, 392, 394, 396 may be similar in configuration and/orfunctionality to similarly named and/or numbered components as describedherein. In some embodiments, the backflow management device 350 (and/orportions thereof) may comprise an automatic backflow detection and/ormanagement program, system, and/or platform programmed and/or otherwiseconfigured to execute, conduct, and/or facilitate the method 500 of FIG.5 herein, and/or portions thereof.

Referring now to FIG. 4 , a perspective diagram of a system 400according to some embodiments is shown. In some embodiments, the system400 may comprise an indoor sanitary, sewer, and/or other drain system ofa building 408 (and/or other structure). The system 400 may comprise,for example, an outlet 408-2 coupled to a drain pipe 408-4. According tosome embodiments, the outlet 408-2 and/or the drain pipe 408-4 may becoupled to and/or in fluid communication with a cleanout 408-5. Thecleanout 408-5 may comprise, as depicted for non-limiting example, ahorizontal offshoot that is terminated with an installed backflowmanagement device 450. Cleanouts 408-5 may be oriented in differentmanners (e.g., angled) and/or may comprise different configurations thanthe cleanout 408-5 depicted in FIG. 4 . In some embodiments, theinstalled backflow management device 450 may comprise a threaded plug(e.g., a “smart” plug) that seals and/or closes the cleanout 408-5. Insuch a manner, for example, the installed backflow management device 450may be coupled to detect, measure, identify, analyze, and/or generatealerts based on fluid characteristics within the cleanout 408-5. Instandard non-pressurized drainage setups, for example, no liquid (e.g.,wastewater, sewage, etc.) should be detectable within the cleanout 408-5and/or the presence of any liquid/solids should be transitory in nature(e.g., a splash-back from a point load drainage event). The installedbackflow management device 450 may analyze sensor readings descriptiveof the inside of the cleanout 408-5 to automatically determine whether abackflow event is likely to exist. In the case that such an event isidentified, remedial action (e.g., alerts, automatic scheduling, and/orautomatic shutoffs) may be initiated by the installed backflowmanagement device 450, in accordance with embodiments described herein.

Fewer or more components 408, 408-2, 408-4, 408-5, 450 and/or variousconfigurations of the depicted components 408, 408-2, 408-4, 408-5, 450may be included in the system 400 without deviating from the scope ofembodiments described herein. In some embodiments, the components 408,408-2, 408-4, 408-5, 450 may be similar in configuration and/orfunctionality to similarly named and/or numbered components as describedherein. In some embodiments, the system 400 (and/or portions thereof)may comprise an automatic backflow detection and/or management program,system, and/or platform programmed and/or otherwise configured toexecute, conduct, and/or facilitate the method 500 of FIG. 5 herein,and/or portions thereof.

III. Backflow Management Methods

Referring now to FIG. 5 , a flow diagram of a method 500 according tosome embodiments is shown. In some embodiments, the method 500 may beperformed and/or implemented by and/or otherwise associated with one ormore specialized and/or specially-programmed computers (e.g., one ormore of the user devices 102 a-b, third-party devices 106, thecontroller devices 110, and/or the apparatus 610 of FIG. 1 and/or FIG. 6herein), computer terminals, computer servers, computer systems and/ornetworks, and/or any combinations thereof (e.g., by one or more backflowmanagement devices as described herein). In some embodiments, the method500 may be embodied in, facilitated by, and/or otherwise associated withvarious input mechanisms and/or interfaces (such as the interface 620 ofFIG. 6 herein).

The process diagrams and flow diagrams described herein do notnecessarily imply a fixed order to any depicted actions, steps, and/orprocedures, and embodiments may generally be performed in any order thatis practicable unless otherwise and specifically noted. While the orderof actions, steps, and/or procedures described herein is generally notfixed, in some embodiments, actions, steps, and/or procedures may bespecifically performed in the order listed, depicted, and/or describedand/or may be performed in response to any previously listed, depicted,and/or described action, step, and/or procedure. Any of the processesand methods described herein may be performed and/or facilitated byhardware, software (including microcode), firmware, or any combinationthereof. For example, a storage medium (e.g., a hard disk, Random AccessMemory (RAM) device, cache memory device, Universal Serial Bus (USB)mass storage device, and/or Digital Video Disk (DVD); e.g., thememory/data storage devices 140, 640 of FIG. 1 and/or FIG. 6 herein) maystore thereon instructions that when executed by a machine (such as acomputerized processor) result in performance according to any one ormore of the embodiments described herein.

According to some embodiments, the method 500 may comprise backflowmanagement device installation, at 502. One or more backflow managementdevices may, for example, be threaded into (or onto) and/or otherwisecoupled to a non-pressurized and/or open-channel flow conduit such as asanitary, storm, and/or sewer drain of a structure (e.g., an outlet). Insome embodiments, the backflow management device may be installedutilizing a specialized wrench as described herein. The backflowmanagement device may be installed by a homeowner, a landlord, asuperintendent, a plumber, and/or another service technician and/oruser. According to some embodiments, the backflow management device maycomprise one or more sensors, input devices, output devices, powerdevices, and/or communications devices.

In some embodiments, the method 500 may comprise monitoring (e.g., by anelectronic processing device and/or sensor/imaging device) for backflow,at 504. One or more sensors, such as pressure transducers, cameras, datatransceivers, range finding devices, and/or other imagery and/or dataacquisition devices, may, for example, be utilized to capture datadescriptive of fluid flow at and/or in the outlet. In some embodiments,data readings and/or values may be captured and/or acquiredautomatically at pre-defined intervals (e.g., every second, minute,hour). According to some embodiments, the data may comprise anyquantity, type, and/or configuration of data that is or becomes known orpracticable. The data may include, for example, a plurality of readingsand/or values descriptive of fluid characteristics such as pressure,flow rate, temperature, distance to surface, turbidity, etc.

According to some embodiments, the method 500 may comprise determining(e.g., by the electronic processing device) whether backflow isdetected, at 506. Any or all data measured and/or acquired by thesensor(s) may be processed by the backflow management device (and/or adevice in communication therewith), for example, to identify that thedata matches a pre-programmed backflow event condition. The data may becompared to one or more thresholds and/or models, for example, toidentify that a condition sensed by the sensor is likely to beindicative of a backflow event. In the case that no backflow event isidentified, the method 500 may proceed back to continue monitoring forbackflow at 504. In the case that a backflow event is identified, themethod 500 may continue to determine whether the backflow eventconstitutes an emergency condition, at 508

The method 500 may comprise, for example, determining (e.g., by theelectronic processing device) whether the backflow event is an emergencyevent, at 508. Stored rules and/or logic (e.g., AI logic) may beutilized, for example, to compare attributes of the backflow event toone or more thresholds and/or criteria to identify whether the eventshould be characterized as an emergency event. In some embodiments,emergency event identification parameters may be customized for eachinstallation location, set and/or edited by a user, and/or may beautomatically updated via wireless communication (e.g., from a remotecontroller/server). In the case that it is determined that an emergencyevent has occurred (e.g., the backflow event is significant enough toconstitute an emergency), the method 500 may proceed to initiate anemergency response, at 510. The emergency response may comprise, forexample, an automatic alert and/or notification to pre-designatedemergency response service personnel such as a twenty-four hour (24-hr)emergency plumbing service, a cleanup/repair company, and/or emergencyresponse personnel (e.g., for potentially unsafe condition remediation).

In the case that it is determined that an emergency event has notoccurred (e.g., the backflow event is not significant enough toconstitute an emergency), the method 500 may proceed to initiate aservice response, at 512. According to some embodiments, a set ofthresholds and/or criteria defining an emergency classification forbackflow events may permit analysis of the rules to result in anindeterminate conclusion/characterization. In such cases, and in thecase that an intermediate characterization of the backflow event isidentified and/or computed, the method 500 may proceed to initiate aservice response, at 512, or may alternatively be configured toimplement a more fail-safe approach in which the indeterminate eventcharacterization causes the method 500 to proceed to initiate theemergency response, at 510.

According to some embodiments, the method 500 may proceed back tocontinue monitoring for backflow at 504 once either the emergencyresponse initiation at 510 or the service response initiation at 512have been triggered and/or completed. In some embodiments, the method500 may also or alternatively store and/or transmit sensed data after anidentification/detection of a backflow event, such as to better documentand/or inform regarding the identified condition.

IV. Backflow Management Apparatus

Referring now to FIG. 6 , a block diagram of an apparatus 610 accordingto some embodiments is shown. In some embodiments, the apparatus 610 maybe similar in configuration and/or functionality to any of the userdevices 102 a-b, the third-party devices 106, the controller device 110,and/or the outlet/backflow management devices 150, 250, 350, 450 of FIG.1 , FIG. 2 , FIG. 3A, FIG. 3B, FIG. 3C, FIG. 3D, FIG. 3E, FIG. 3F, FIG.3G, FIG. 3H, FIG. 31 and/or FIG. 4 herein. The apparatus 610 may, forexample, execute, process, facilitate, and/or otherwise be associatedwith the method/process 500 of FIG. 5 herein, and/or portions thereof.In some embodiments, the apparatus 610 may comprise a processing device612, a transceiver device 614, an input device 616, an output device618, an interface 620, a memory device 640 (storing various programsand/or instructions 642 and data 644), and/or a cooling device 646.According to some embodiments, any or all of the components 612, 614,616, 618, 620, 640, 642, 644, 646 of the apparatus 610 may be similar inconfiguration and/or functionality to any similarly named and/ornumbered components described herein. Fewer or more components 612, 614,616, 618, 620, 640, 642, 644, 646 and/or various configurations of thecomponents 612, 614, 616, 618, 620, 640, 642, 644, 646 be included inthe apparatus 610 without deviating from the scope of embodimentsdescribed herein.

According to some embodiments, the processor 612 may be or include anytype, quantity, and/or configuration of processor that is or becomesknown. The processor 612 may comprise, for example, an Intel® IXP 2800network processor or an Intel® XEON™ Processor coupled with an Intel®E6501 chipset. In some embodiments, the processor 612 may comprisemultiple interconnected processors, microprocessors, and/ormicro-engines. According to some embodiments, the processor 612 (and/orthe apparatus 610 and/or other components thereof) may be supplied powervia a power supply (not shown), such as a battery, an AlternatingCurrent (AC) source, a Direct Current (DC) source, an AC/DC adapter,solar cells, and/or an inertial generator. In the case that theapparatus 610 comprises a server, such as a blade server, necessarypower may be supplied via a standard AC outlet, power strip, surgeprotector, and/or Uninterruptible Power Supply (UPS) device.

In some embodiments, the transceiver device 614 may comprise any type orconfiguration of communication device that is or becomes known orpracticable. The transceiver device 614 may, for example, comprise aNetwork Interface Card (NIC), a telephonic device, a cellular networkdevice, a router, a hub, a modem, and/or a communications port or cable.According to some embodiments, the transceiver device 614 may also oralternatively be coupled to the processor 612. In some embodiments, thetransceiver device 614 may comprise an IR, RF, Bluetooth™, Near-FieldCommunication (NFC), and/or Wi-Fi® network device coupled to facilitatecommunications between the processor 612 and another device (not shown).

According to some embodiments, the input device 616 and/or the outputdevice 618 may be communicatively coupled to the processor 612 (e.g.,via wired and/or wireless connections and/or pathways) and they maygenerally comprise any types or configurations of input and outputcomponents and/or devices that are or become known, respectively. Theinput device 616 may comprise, for example, a keyboard that allows anoperator of the apparatus 610 to interface with the apparatus 610 (e.g.,a user, such as to initiate automatic backflow condition monitoringand/or management, as described herein). The output device 618 may,according to some embodiments, comprise a display screen and/or otherpracticable output component and/or device. The output device 618 may,for example, provide an interface (such as the interface 620) via whichbackflow modeling, assessment, and/or analysis data or information isprovided to a user (e.g., via a website and/or mobile application).According to some embodiments, the input device 616 and/or the outputdevice 618 may comprise and/or be embodied in a single device, such as atouch-screen monitor or display.

The memory device 640 may comprise any appropriate information storagedevice that is or becomes known or available, including, but not limitedto, units and/or combinations of magnetic storage devices (e.g., a harddisk drive), optical storage devices, and/or semiconductor memorydevices, such as RAM devices, Read Only Memory (ROM) devices, SingleData Rate Random Access Memory (SDR-RAM), Double Data Rate Random AccessMemory (DDR-RAM), and/or Programmable Read Only Memory (PROM). Thememory device 640 may, according to some embodiments, store one or moreof monitoring instructions 642-1, response instructions 642-2, and/orinterface instructions 642-3, sensor data 644-1, building data 644-2,user data 644-3, and/or contact data 644-4. In some embodiments, themonitoring instructions 642-1, response instructions 642-2, and/orinterface instructions 642-3, sensor data 644-1, building data 644-2,user data 644-3, and/or contact data 644-4 may be utilized by theprocessor 612 to provide output information via the output device 618and/or the transceiver device 614.

According to some embodiments, the monitoring instructions 642-1 may beoperable to cause the processor 612 to process sensor data 644-1,building data 644-2, user data 644-3, and/or contact data 644-4 inaccordance with embodiments as described herein. Sensor data 644-1,building data 644-2, user data 644-3, and/or contact data 644-4 receivedvia the input device 616 and/or the transceiver device 614 may, forexample, be analyzed, sorted, filtered, decoded, decompressed, ranked,scored, plotted, and/or otherwise processed by the processor 612 inaccordance with the monitoring instructions 642-1. In some embodiments,sensor data 644-1, building data 644-2, user data 644-3, and/or contactdata 644-4 may be fed by the processor 612 through one or moremathematical and/or statistical formulas and/or models in accordancewith the monitoring instructions 642-1 to acquire and/or direct theacquisition of sensor data descriptive of an outlet conduit and/or fluidconditions thereof, as described herein.

In some embodiments, the response instructions 642-2 may be operable tocause the processor 612 to process sensor data 644-1, building data644-2, user data 644-3, and/or contact data 644-4 in accordance withembodiments as described herein. Sensor data 644-1, building data 644-2,user data 644-3, and/or contact data 644-4 received via the input device616 and/or the transceiver device 614 may, for example, be analyzed,sorted, filtered, decoded, decompressed, ranked, scored, plotted, and/orotherwise processed by the processor 612 in accordance with the responseinstructions 642-2. In some embodiments, sensor data 644-1, buildingdata 644-2, user data 644-3, and/or contact data 644-4 may be fed by theprocessor 612 through one or more mathematical and/or statisticalformulas and/or models in accordance with the response instructions642-2 to identify contact information for a service and/or responsetechnician and automatically transmit an alert or request thereto, asdescribed herein.

According to some embodiments, the interface instructions 642-3 may beoperable to cause the processor 612 to process sensor data 644-1,building data 644-2, user data 644-3, and/or contact data 644-4 inaccordance with embodiments as described herein. Sensor data 644-1,building data 644-2, user data 644-3, and/or contact data 644-4 receivedvia the input device 616 and/or the transceiver device 614 may, forexample, be analyzed, sorted, filtered, decoded, decompressed, ranked,scored, plotted, and/or otherwise processed by the processor 612 inaccordance with the interface instructions 642-3. In some embodiments,sensor data 644-1, building data 644-2, user data 644-3, and/or contactdata 644-4 may be fed by the processor 612 through one or moremathematical and/or statistical formulas and/or models in accordancewith the interface instructions 642-3 to provide various interfaces toend-users, consumers, companies, and/or other users to facilitatebackflow management, as described herein.

In some embodiments, the apparatus 610 may comprise the cooling device646. According to some embodiments, the cooling device 646 may becoupled (physically, thermally, and/or electrically) to the processor612 and/or to the memory device 640. The cooling device 646 may, forexample, comprise a fan, heat sink, heat pipe, radiator, cold plate,and/or other cooling component or device or combinations thereof,configured to remove heat from portions or components of the apparatus610.

Any or all of the exemplary instructions and data types described hereinand other practicable types of data may be stored in any number, type,and/or configuration of memory devices that is or becomes known. Thememory device 640 may, for example, comprise one or more data tables orfiles, databases, table spaces, registers, and/or other storagestructures. In some embodiments, multiple databases and/or storagestructures (and/or multiple memory devices 640) may be utilized to storeinformation associated with the apparatus 610. According to someembodiments, the memory device 640 may be incorporated into and/orotherwise coupled to the apparatus 610 (e.g., as shown) or may simply beaccessible to the apparatus 610 (e.g., externally located and/orsituated).

V. Rules of Interpretation

Throughout the description herein and unless otherwise specified, thefollowing terms may include and/or encompass the example meaningsprovided. These terms and illustrative example meanings are provided toclarify the language selected to describe embodiments both in thespecification and in the appended claims, and accordingly, are notintended to be generally limiting. While not generally limiting andwhile not limiting for all described embodiments, in some embodiments,the terms are specifically limited to the example definitions and/orexamples provided. Other terms are defined throughout the presentdescription.

Numerous embodiments are described in this patent application, and arepresented for illustrative purposes only. The described embodiments arenot, and are not intended to be, limiting in any sense. The presentlydisclosed invention(s) are widely applicable to numerous embodiments, asis readily apparent from the disclosure. One of ordinary skill in theart will recognize that the disclosed invention(s) may be practiced withvarious modifications and alterations, such as structural, logical,software, and electrical modifications. Although particular features ofthe disclosed invention(s) may be described with reference to one ormore particular embodiments and/or drawings, it should be understoodthat such features are not limited to usage in the one or moreparticular embodiments or drawings with reference to which they aredescribed, unless expressly specified otherwise.

The present disclosure is neither a literal description of allembodiments of the invention nor a listing of features of the inventionthat must be present in all embodiments. A description of an embodimentwith several components or features does not imply that all or even anyof such components and/or features are required. On the contrary, avariety of optional components are described to illustrate the widevariety of possible embodiments of the present invention(s). Unlessotherwise specified explicitly, no component and/or feature is essentialor required. Although a product may be described as including aplurality of components, aspects, qualities, characteristics and/orfeatures, that does not indicate that all of the plurality are essentialor required. Various other embodiments within the scope of the describedinvention(s) include other products that omit some or all of thedescribed plurality. A description of an embodiment with severalcomponents or features does not imply that all or even any of suchcomponents and/or features are required. On the contrary, a variety ofoptional components are described to illustrate the wide variety ofpossible embodiments of the present invention(s). Unless otherwisespecified explicitly, no component and/or feature is essential orrequired.

Neither the Title (set forth at the beginning of the first page of thispatent application) nor the Abstract (set forth at the end of thispatent application) is to be taken as limiting in any way as the scopeof the disclosed invention(s). Headings of sections provided in thispatent application are for convenience only, and are not to be taken aslimiting the disclosure in any way.

All definitions, as defined and used herein, should be understood tocontrol over dictionary definitions, definitions in documentsincorporated by reference, and/or ordinary meanings of the definedterms. The terms and expressions which have been employed herein areused as terms of description and not of limitation, and there is nointention, in the use of such terms and expressions, of excluding anyequivalents of the features shown and described (or portions thereof),and it is recognized that various modifications are possible within thescope of the claims. Accordingly, the claims are intended to cover allsuch equivalents.

The term “product” means any machine, manufacture and/or composition ofmatter as contemplated by 35 U.S.C. § 101, unless expressly specifiedotherwise.

The terms “an embodiment”, “embodiment”, “embodiments”, “theembodiment”, “the embodiments”, “one or more embodiments”, “someembodiments”, “one embodiment” and the like mean “one or more (but notall) disclosed embodiments”, unless expressly specified otherwise.Reference throughout this specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, appearances of the phrases “in oneembodiment” or “in an embodiment” in various places throughout thisspecification are not necessarily all referring to the same embodiment.Furthermore, the particular features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments.

A reference to “another embodiment” in describing an embodiment does notimply that the referenced embodiment is mutually exclusive with anotherembodiment (e.g., an embodiment described before the referencedembodiment), unless expressly specified otherwise.

The indefinite articles “a” and “an,” as used herein in thespecification and in the claims, unless clearly indicated to thecontrary, should be understood to mean “at least one” or “one or more”.

The phrase “and/or,” as used herein in the specification and in theclaims, should be understood to mean “either or both” of the elements soconjoined, i.e., elements that are conjunctively present in some casesand disjunctively present in other cases. Other elements may optionallybe present other than the elements specifically identified by the“and/or” clause, whether related or unrelated to those elementsspecifically identified, unless clearly indicated to the contrary.

The term “plurality” means “two or more”, unless expressly specifiedotherwise.

The term “herein” means “in the present application, including anythingwhich may be incorporated by reference”, unless expressly specifiedotherwise.

The phrase “at least one of”, when such phrase modifies a plurality ofthings (such as an enumerated list of things) means any combination ofone or more of those things, unless expressly specified otherwise. Forexample, the phrase at least one of a widget, a car and a wheel meanseither (i) a widget, (ii) a car, (iii) a wheel, (iv) a widget and a car,(v) a widget and a wheel, (vi) a car and a wheel, or (vii) a widget, acar and a wheel.

The phrase “based on” does not mean “based only on”, unless expresslyspecified otherwise. In other words, the phrase “based on” describesboth “based only on” and “based at least on”.

The disclosure of numerical ranges should be understood as referring toeach discrete point within the range, inclusive of endpoints, unlessotherwise noted. Unless otherwise indicated, all numbers expressingquantities of components, molecular weights, percentages, temperatures,times, and so forth, as used in the specification or claims are to beunderstood as being modified by the term “about.” Accordingly, unlessotherwise implicitly or explicitly indicated, or unless the context isproperly understood by a person of ordinary skill in the art to have amore definitive construction, the numerical parameters set forth areapproximations that may depend on the desired properties sought and/orlimits of detection under standard test conditions/methods, as known tothose of ordinary skill in the art. When directly and explicitlydistinguishing embodiments from discussed prior art, the embodimentnumbers are not approximates unless the word “about” is recited.Whenever “substantially,” “approximately,” “about,” or similar languageis explicitly used in combination with a specific value, variations upto and including ten percent (10%) of that value are intended, unlessexplicitly stated otherwise.

Directions and other relative references may be used to facilitatediscussion of the drawings and principles herein, but are not intendedto be limiting. For example, certain terms may be used such as “inner,”“outer”, “upper,” “lower,” “top,” “bottom,” “interior,” “exterior,”“left,” right,” “front,” “back,” “rear,” and the like. Such terms areused, where applicable, to provide some clarity of description whendealing with relative relationships, particularly with respect to theillustrated embodiments. Such terms are not, however, intended to implyabsolute relationships, positions, and/or orientations. For example,with respect to an object, an “upper” part can become a “lower” partsimply by turning the object over. Nevertheless, it is still the samepart and the object remains the same. Similarly, while the terms“horizontal” and “vertical” may be utilized herein, such terms may referto any normal geometric planes regardless of their orientation withrespect to true horizontal or vertical directions (e.g., with respect tothe vector of gravitational acceleration).

Where a limitation of a first claim would cover one of a feature as wellas more than one of a feature (e.g., a limitation such as “at least onewidget” covers one widget as well as more than one widget), and where ina second claim that depends on the first claim, the second claim uses adefinite article “the” to refer to the limitation (e.g., “the widget”),this does not imply that the first claim covers only one of the feature,and this does not imply that the second claim covers only one of thefeature (e.g., “the widget” can cover both one widget and more than onewidget).

Each process (whether called a method, algorithm or otherwise)inherently includes one or more steps, and therefore all references to a“step” or “steps” of a process have an inherent antecedent basis in themere recitation of the term ‘process’ or a like term. Accordingly, anyreference in a claim to a ‘step’ or ‘steps’ of a process has sufficientantecedent basis.

Further, although process steps, algorithms or the like may be describedin a sequential order, such processes may be configured to work indifferent orders. In other words, any sequence or order of steps thatmay be explicitly described does not necessarily indicate a requirementthat the steps be performed in that order. The steps of processesdescribed herein may be performed in any order practical. Further, somesteps may be performed simultaneously despite being described or impliedas occurring non-simultaneously (e.g., because one step is describedafter the other step). Moreover, the illustration of a process by itsdepiction in a drawing does not imply that the illustrated process isexclusive of other variations and modifications thereto, does not implythat the illustrated process or any of its steps are necessary to theinvention, and does not imply that the illustrated process is preferred.

Although a process may be described as including a plurality of steps,that does not indicate that all or even any of the steps are essentialor required. Various other embodiments within the scope of the describedinvention(s) include other processes that omit some or all of thedescribed steps. Unless otherwise specified explicitly, no step isessential or required.

When an ordinal number (such as “first”, “second”, “third” and so on) isused as an adjective before a term, that ordinal number is used (unlessexpressly specified otherwise) merely to indicate a particular feature,such as to distinguish that particular feature from another feature thatis described by the same term or by a similar term. For example, a“first widget” may be so named merely to distinguish it from, e.g., a“second widget”. Thus, the mere usage of the ordinal numbers “first” and“second” before the term “widget” does not indicate any otherrelationship between the two widgets, and likewise does not indicate anyother characteristics of either or both widgets. For example, the mereusage of the ordinal numbers “first” and “second” before the term“widget” (1) does not indicate that either widget comes before or afterany other in order or location; (2) does not indicate that either widgetoccurs or acts before or after any other in time; and (3) does notindicate that either widget ranks above or below any other, as inimportance or quality. In addition, the mere usage of ordinal numbersdoes not define a numerical limit to the features identified with theordinal numbers. For example, the mere usage of the ordinal numbers“first” and “second” before the term “widget” does not indicate thatthere must be no more than two widgets.

An enumerated list of items (which may or may not be numbered) does notimply that any or all of the items are mutually exclusive, unlessexpressly specified otherwise. Likewise, an enumerated list of items(which may or may not be numbered) does not imply that any or all of theitems are comprehensive of any category, unless expressly specifiedotherwise. For example, the enumerated list “a computer, a laptop, aPDA” does not imply that any or all of the three items of that list aremutually exclusive and does not imply that any or all of the three itemsof that list are comprehensive of any category.

When a single device or article is described herein, more than onedevice or article (whether or not they cooperate) may alternatively beused in place of the single device or article that is described.Accordingly, the functionality that is described as being possessed by adevice may alternatively be possessed by more than one device or article(whether or not they cooperate).

Similarly, where more than one device or article is described herein(whether or not they cooperate), a single device or article mayalternatively be used in place of the more than one device or articlethat is described. For example, a plurality of computer-based devicesmay be substituted with a single computer-based device. Accordingly, thevarious functionality that is described as being possessed by more thanone device or article may alternatively be possessed by a single deviceor article.

The functionality and/or the features of a single device that isdescribed may be alternatively embodied by one or more other deviceswhich are described but are not explicitly described as having suchfunctionality and/or features. Thus, other embodiments need not includethe described device itself, but rather can include the one or moreother devices which would, in those other embodiments, have suchfunctionality/features.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. On the contrary, such devices need only transmit to eachother as necessary or desirable, and may actually refrain fromexchanging data most of the time. For example, a machine incommunication with another machine via the Internet may not transmitdata to the other machine for weeks at a time. In addition, devices thatare in communication with each other may communicate directly orindirectly through one or more intermediaries.

“Determining” something can be performed in a variety of manners andtherefore the term “determining” (and like terms) includes calculating,computing, deriving, looking up (e.g., in a table, database or datastructure), ascertaining and the like

The terms “including”, “comprising” and variations thereof mean“including but not limited to”, unless expressly specified otherwise. Asused herein, “comprising” means “including,” and the singular forms “a”or “an” or “the” include plural references unless the context clearlydictates otherwise. The term “or” refers to a single element of statedalternative elements or a combination of two or more elements, unlessthe context clearly indicates otherwise

The present disclosure provides, to one of ordinary skill in the art, anenabling description of several embodiments and/or inventions. Some ofthese embodiments and/or inventions may not be claimed in the presentapplication, but may nevertheless be claimed in one or more continuingapplications that claim the benefit of priority of the presentapplication. Applicants intend to file additional applications to pursuepatents for subject matter that has been disclosed and enabled but notclaimed in the present application.

While several embodiments of the present disclosure have been describedand illustrated herein, those of ordinary skill in the art will readilyenvision a variety of other means and/or structures for performing thefunctions and/or obtaining the results and/or one or more of theadvantages described herein, and each of such variations and/ormodifications is deemed to be within the scope of the presentdisclosure. More generally, those skilled in the art will readilyappreciate that all parameters, dimensions, materials, andconfigurations described herein are meant to be exemplary and that theactual parameters, dimensions, materials, and/or configurations willdepend upon the specific application or applications for which theteachings of the present disclosure is/are used.

Those skilled in the art will recognize, or be able to ascertain usingno more than routine experimentation, many equivalents to the specificembodiments of the disclosure described herein. It is, therefore, to beunderstood that the foregoing embodiments are presented by way ofexample only and that, within the scope of the appended claims andequivalents thereto, the disclosure may be practiced otherwise than asspecifically described and claimed. The present disclosure is directedto each individual feature, system, article, material, kit, and/ormethod described herein. In addition, any combination of two or moresuch features, systems, articles, materials, kits, and/or methods, ifsuch features, systems, articles, materials, kits, and/or methods arenot mutually inconsistent, is included within the scope of the presentdisclosure.

Various modifications of the invention and many further embodimentsthereof, in addition to those shown and described herein, will becomeapparent to those skilled in the art from the full contents of thisdocument, including references to any scientific and patent literaturecited herein. The subject matter herein contains important information,exemplification and guidance that can be adapted to the practice of thisinvention in its various embodiments and equivalents thereof. It will beunderstood that various modifications can be made to the embodiments ofthe present disclosure herein without departing from the scope thereof.Therefore, the above description should not be construed as limiting thedisclosure, but merely as embodiments thereof. Those skilled in the artwill envision other modifications within the scope of the invention asdefined by the claims appended hereto.

What is claimed is:
 1. An automatic backflow management system,comprising: a backflow management device comprising: a housingcomprising threads and defining an interior volume, the threads beingengaged with corresponding threads of a non-pressurized fluid conduit; acover coupled to seal the interior volume, the cover comprising a bore;and an electronic processing device disposed within the interior volume;a fluid sensor disposed within the interior volume, in communicationwith the electronic processing device, and oriented to detect fluidproperties through the bore; a wireless communication device disposedwithin the interior volume and in communication with the electronicprocessing device; and a memory device storing instructions that whenexecuted by the electronic processing device result in: receiving datadescriptive of a fluid property of a fluid in the non-pressurized fluidconduit; identifying, by the electronic processing device and by acomparison of the data to stored rules, an occurrence of a backflowevent; and automatically transmitting, by the wireless communicationdevice, an alert descriptive of the identified backflow eventoccurrence.
 2. The automatic backflow management system of claim 1,wherein the instructions, when executed, further result in:automatically transmitting, by the wireless communication device and inresponse to the identifying of the backflow event, a shutoff command toa fluid inlet device.
 3. The automatic backflow management system ofclaim 1, further comprising: the fluid inlet device.
 4. The automaticbackflow management system of claim 1, wherein the housing furthercomprises a raised nub defining a plurality of sides extending axiallyfrom the housing.
 5. The automatic backflow management system of claim1, wherein the non-pressurized fluid conduit comprises a section of atleast one of a sanitary and a sewer effluent system.
 6. The automaticbackflow management system of claim 1, wherein the fluid comprisessewage.
 7. The automatic backflow management system of claim 1, whereinthe fluid property of the fluid comprises a distance of a surface of thefluid from the fluid sensor.
 8. The automatic backflow management systemof claim 1, wherein the fluid property of the fluid comprises a pressureexerted by the fluid.
 9. The automatic backflow management system ofclaim 8, wherein the fluid property of the fluid comprises a measurementof an amount of the pressure exerted by the fluid.
 10. An automaticbackflow management method, comprising: receiving, (i) by an electronicprocessing device disposed within an interior volume of a housing of abackflow management device, the housing of the backflow managementdevice comprising exterior threads that are engaged to couple thehousing of the backflow management device with corresponding threads ofa non-pressurized fluid conduit, and the backflow management devicecomprising a cover coupled to seal the interior volume, and wherein thecover comprises a bore, and (ii) from a fluid sensor disposed within theinterior volume, the fluid sensor being in in communication with theelectronic processing device and being oriented to detect fluidproperties through the bore, (iii) data descriptive of a fluid propertyof a fluid in the non-pressurized fluid conduit; identifying, by anexecution of instructions by the electronic processing device, theinstructions being stored on a memory device disposed within theinterior volume and in communication with the electronic processingdevice, and by a comparison of the data to stored rules, an occurrenceof a backflow event; and automatically transmitting, by a wirelesscommunication device disposed within the interior volume and incommunication with the electronic processing device, an alertdescriptive of the identified backflow event occurrence.
 11. Theautomatic backflow management method of claim 10, further comprising:automatically transmitting, by the wireless communication device and inresponse to the identifying of the backflow event, a shutoff command toa fluid inlet device.
 12. The automatic backflow management method ofclaim 11, wherein the fluid inlet device comprises a valve that controlsa pressurized fluid distribution system.
 13. The automatic backflowmanagement method of claim 10, wherein the housing further comprises araised nub defining a plurality of sides extending axially from thehousing.
 14. The automatic backflow management method of claim 10,wherein the non-pressurized fluid conduit comprises a section of atleast one of a sanitary and a sewer effluent system.
 15. The automaticbackflow management method of claim 10, wherein the fluid comprisessewage.
 16. The automatic backflow management method of claim 10,wherein the fluid property of the fluid comprises a distance of asurface of the fluid from the fluid sensor.
 17. The automatic backflowmanagement method of claim 10, wherein the fluid property of the fluidcomprises a pressure exerted by the fluid.
 18. The automatic backflowmanagement system of claim 17, wherein the fluid property of the fluidcomprises a measurement of an amount of the pressure exerted by thefluid.